Determining vehicle dwell time within predetermined zones

ABSTRACT

Systems and methods for determining the amount of time that an object occupies a predetermined space are provided. In one implementation, a system comprises a sensor configured to determine a start time when a recognizable object enters a predetermined space. The sensor is further configured to determine an end time when the recognizable object leaves the predetermined space. The system also includes a processing device configured to determine an elapsed time, based on the start time and the end time, when the recognizable object remains in the predetermined space.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a Continuation of application Ser. No. 15/996,814 filed Jun. 4,2018, which in turn claims priority to U.S. Provisional PatentApplication Ser. No. 62/583,239, filed Nov. 8, 2017, entitled, “Systemsand Methods for Determining the Time that an Object Remains in aPredetermined Location,” the entirety of which is incorporated byreference herein.

FIELD OF THE INVENTION

The present invention is directed to systems, methods, and analysissoftware for counting a number of vehicles that occupy predeterminedzones over a predetermined time period and for determining the length oftime (dwell time) that each vehicle remains within the predeterminedzones.

BACKGROUND

Many service businesses strive to provide a satisfying experience forits customers so that customers will continue to visit theirestablishments. For example, businesses that provide quick oil changesfor vehicles may try to perform an oil change service within a certainamount of time. Otherwise, if the service time is too long, customersmay become disgruntled and refuse to revisit the establishments.According to another example, a quick service restaurant (QSR) may wishto provide a speedy process for ordering, paying for, and receiving foodsuch that a drive-through customer can place an order, pay for theorder, and pick up his or her food all within a reasonable amount oftime.

Therefore, there is a need to monitor the amount of time that a customerhas to wait to receive a service and to automatically monitor the amountof time that it takes to perform various services for the customer.There is also a need to gather and analyze statistics related to servicewait times.

SUMMARY

The present disclosure generally describes various systems and methodsfor determining the amount of time that an object occupies apredetermined zone. For example, the predetermined zone may be a spacewhere a service is performed for a customer, and may be occupied by aperson, vehicle, or other object that is being serviced. In oneembodiment, a system for determining vehicle dwell time may include afirst camera configured to obtain image data of a first predeterminedzone and a second camera configured to obtain image data of a secondpredetermined zone. The system may further include a processor and adisplay screen. The processor may be configured to utilize the imagedata from the first camera to determine if a first condition is met, thefirst condition being met when any vehicle occupies at least an amountof space in the first predetermined zone greater than a firstpredetermined threshold. The processor may also be configured torecognize image characteristics of a first vehicle in the firstpredetermined zone. Also, the processor may determine a first start timewhen the first condition is first met by the first vehicle and a firstend time, after the first start time, when the first condition is nolonger met by the first vehicle, and calculate, from the first starttime and first end time, a first dwell time that the first vehicleremains in the first predetermined zone. Utilizing the image data fromthe second camera, the processor is further configured to determine if asecond condition is met, the second condition being met when any vehicleoccupies at least an amount of space in the second predetermined zonegreater than a second predetermined threshold. The processor may alsorecognize the image characteristics of the first vehicle in the secondpredetermined zone, and determine a second start time when the secondcondition is first met by the first vehicle and a second end time, afterthe second start time, when the second condition is no longer met by thefirst vehicle. The processor is further configured to calculate, fromthe second start time and second end time, a second dwell time that thefirst vehicle remains in the second predetermined zone. The processorcan also utilize the first dwell time and second dwell time to calculatea total dwell time, and display an image of the first vehicle and thetotal dwell time on the display screen.

In another embodiment of a system, a camera may be configured to capturean image of a vehicle in a predetermined space. Also, a processor may beconfigured to determine a start time when the vehicle enters thepredetermined space, determine an end time when the vehicle leaves thepredetermined space, and calculate an elapsed time, based on the starttime and the end time, when the vehicle remained in the predeterminedspace.

According to a method for monitoring service time, an exemplary methodcomprises a step of determining a start time when a vehicle enters apredetermined space. Another step includes determining an end time whenthe vehicle leaves the predetermined space. Also, the method may includedetermining a dwell time that the vehicle remains in the predeterminedspace, the dwell time being determined from the start time and the endtime.

Other embodiments of the present invention may be understood from anunderstanding of the detailed description and are believed to beincluded within the spirit and scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system for monitoring servicetimes or dwell times, according to one embodiment.

FIG. 2 is a block diagram illustrating the computer system shown in FIG.1, according to one embodiment.

FIG. 3 is an exemplary display view of a customer display device forshowing aspects of a service performed for a customer, according to oneembodiment.

FIG. 4 is a first exemplary display view of a computer system displayfor showing aspects of services at a shop, according to one embodiment.

FIG. 5 is a second exemplary display view of the computer system displayfor showing aspects of services at the shop, according to oneembodiment.

FIG. 6 is a third exemplary display view of the computer system displayfor showing aspects of services at multiple locations of a store,according to one embodiment.

FIG. 7 is a diagram showing a plan view of a vehicle lane that includesmultiple predetermined zones where the presence of vehicles is detected,according to one embodiment.

FIG. 8 is a screen display view of a customer mobile device for showingwait times at multiple shop locations, according to one embodiment.

FIG. 9 is a flow diagram showing a method for determining a time that anobject remains at a location, according to one embodiment.

FIGS. 10A and 10B together form a flow diagram showing a method fordetermining dwell times at first and second predetermined zones,according to one embodiment.

DETAILED DESCRIPTION

The present disclosure is generally directed to systems and methods formonitoring service wait times. Image data may be obtained to determinewhether or not a recognizable object occupies a predetermined space orzone. The predetermined zone is a place where the object receives sometype of service or waits for service. For example, the objects may bevehicles (e.g., trucks, cars, motorcycles, etc.) or, in alternativeembodiments, may be humans (e.g., the customers themselves) or otherobjects that can be identified by recognition software.

Start times and end times of when the objects occupy the predeterminedspaces are used to determine a dwell time (i.e., time that the objectremains in the one location). From the total dwell times, statisticalanalysis can be performed to determine average service times within adesignated time frame (e.g., one hour, one day, etc.) for a number ofcustomers, average service times for a particular shop, average servicetimes for a group of shops in a franchise, and other factors.

Image data can be obtained using any suitable type of cameras. Forexample, certain types of conventional cameras may typically be used tomonitor highways, but conventional software used with those systems maysimply count the number of cars that pass along a road or lane. In thepresent application, software is used to provide further processing tokeep track of the times that vehicles remain in designated locations andanalyze data regarding service wait times.

The way in which the software detects that a vehicle is present within apredetermined zone may include determining that a predetermine volumehas displaced an otherwise empty space. In other words, in an initialstate where no object is present in the predetermined zone, the imagedata includes certain characteristics. When an object is present, atleast a certain amount of change is detected in the image data when theimage data is replaced. When the amount of change is greater than acertain minimum threshold, the software enables the detection of thepresence of an object. This algorithm and other algorithms may be usedto detect the presence of a vehicle.

The image data and service time analysis can be displayed for thecustomer's view so that the customer may be informed of the status ofthe service. In addition, the image data and service times can also bedisplayed for the viewing by a shop manager or other serviceprofessional.

In some embodiments, the system of the present disclosure allows serviceprofessionals to set goals regarding service times. The goals may beused as an incentive to motivate employees to provide service tocustomers within a reasonable amount of time. For instance, in a quickservice restaurant (QSR) or fast-food restaurant, goals may be set forvarious wait times, particularly in a drive-through lane. A first waittime may be defined as a time that a customer has to wait in line beforethey are able to place an order. A second wait time may be defined as anelapsed time from when the customer finishes placing the order to whenthe customer reaches a place where the customer can pay for the order. Athird time may be defined as a time between paying for the order andactually receiving the food order.

Times can be monitored at each of a number of zones where a vehicle maywait. Then, the total wait time can be determined for each vehicle. Whenservice times are determined and compared with service goals, theservice professionals may be motivated to fulfill orders and/or performservices more quickly. If it is determined that service times are toolong, the businesses (e.g., quick oil change facilities, QSRs, or otherstores or shops) can analyze various aspects of their business processesto determine ways to speed up the services provided to its customers.

These and other advantages and benefits can be achieved using theembodiments described below. It should be noted that the followingembodiments are not meant to limit the invention in any way, but areprovided merely as examples of possible implementations and may includeother embodiments as will become known from an understanding of thepresent disclosure.

FIG. 1 is a block diagram showing an embodiment of a system 10 formonitoring service times. In this system 10, one or more cameras 12 areused for monitoring one or more areas or zones where a customer waitsfor service or where service may already be in the process of beingperformed. The cameras 12 may include video cameras, such as IP cameras,analog/AHD/TVI cameras, general surveillance cameras, fish-eye cameras,etc. The system 10 also includes a computer system 14 that receivesimage signals (e.g., video signals) from the cameras 12.

According to some embodiments, the cameras 12 and computer system 14 maybe configured as a system in and of itself for monitoring serviceinformation at one facility, store, shop, etc. In this respect, thesingle-shop information can be used to monitor service times at just theone shop without communications with other shops.

However, in other embodiments, the system 10 may be configured to gatherdata from other shops in order that a franchise or other conglomerationof shops can compare service data at each of its respective shops. Tothis end, the system 10 may further include a point-of-sale (POS) system16 comprising, for example, one or more POS terminals, a POS router, andother suitable POS components. The POS system 16 may be configured tocommunicate sales information as needed, although in some embodimentsthe POS system 16 may be omitted. The system 10 also includes a gateway18, such as a broadband gateway, for communicating with other computersystems over the Internet 20 or other local area or wide areacommunication network. The service information can be communicated fromeach of a number of shops via the Internet 20 to a location wait timeserver 22.

The location wait time server 22 may be configured to receive serviceinformation from multiple shops located at multiple locations. In someembodiments, the location wait time server 22 can process the serviceinformation to determine an estimated wait time at each shop. Thelocation wait time server 22 may be configured to upload informationthat will be made available to multiple customers throughout a region,whereby the customers can access the service information to see theestimated wait times at multiple locations. With this information, acustomer, depending on his or her location and schedule, can decidewhich shop to visit to receive service.

Therefore, FIG. 1 shows the basic connectivity of the various componentsin the system 10, comprises, among other things, the cameras 12 (e.g.,IP cameras) arranged to capture predetermined locations or zones relatedto services. For example, the locations or zones may include servicebays of a quick lubrication oil change business. Another example mayinclude vehicle lane locations where vehicles may temporarily stop forcertain services to be performed, such as a first location where acustomer places an order at a drive-through lane of a quick servicerestaurant (QSR) or fast food restaurant. Other locations may includezones in front of a payment window or a food pick-up window.

In addition to vehicles, the system 10 may also monitor people or otherrecognizable object within predetermined locations or zones wherecustomers may be waiting in line to be served (e.g., at a bank, DMV,etc.). Multiple cameras 12 may be used to view predetermined locationsfrom a number of different angles and/or to view multiple locationsthroughout a series of service processes.

FIG. 2 is a block diagram of an embodiment of the computer system 14shown in FIG. 1. The computer system 14, according to this embodiment,includes a processing device 26 (e.g., processor, microprocessor,microcontroller, etc.) for executing logic processes of the computersystem 14. The computer system 14 also includes a memory device 28 ormemory, a camera interface 30, a digital video recorder or network videorecorder (DVR/NVR) 32, one or more display devices 34, otherinput/output (I/O) devices (e.g., computer peripherals) 36, and a router38, each interconnected with the processing device 26 via a businterface 40.

The computer system 14 includes hardware, software, and/or firmware forenabling the execution of programs or methods for monitoring serviceactivities associated with one or more customers. For example, thememory device 28 may store a software or firmware module for monitoringservice, such as an object/space tracking module 42. The object/spacetracking module 42, for instance, may be configured to track one or morepredetermined spaces or zones where services are performed and determinewhether or not a recognizable object occupies those spaces or zones andhow long the object remains in those spaces or zones.

For example, at an oil change shop, the object/space tracking module 42can monitor whether a vehicle is positioned in a bay where an oil changecan be conducted. Also, in the oil change scenario, the object/spacetracking module 42 may be configured to determine how long each vehicleremains in the predetermined zone, which is an indication of how long ittakes for the workers at the shop to service the vehicle.

The camera interface 30 may further include a PoE (power over Ethernet)switch or other network switch for for receiving video data from thecameras 12 and switching the IP cameras 12 to the processing device 26.In some embodiments, the video data can be sent directly to one or moredisplay devices 34. For example, live video feed can be provided to adisplay device 34 that is provided for a customer, whereby the displaydevice 34 in this case may be located in a customer waiting area of anoil change shop. Other live feed can be provided to a display device 34that may be located in a manager's office, for example, and may beconfigured for the viewing by one or more workers at the shop. Multipleviews from multiple cameras 12 may be provided to each display device 34according to various embodiments.

In addition to live feed, the video information can also be recorded andstored temporarily or long term in the DVR/NVR 32. Therefore, if anissue arises with respect to service times taking much longer thanexpected, then video footage can be retrieved and viewed to determinewhy the service took so long. The processing device 26 may be configuredto analyze the video information, either directly from the camerainterface 30 or from the DVR/NVR 32. The video information can beanalyzed using image recognition processes to determine characteristicsof the images. For example, if a shop intends to track vehicles, thenthe processing device 26 may be configured to recognize when an objectin a predetermined location can be identified as a vehicle and how todistinguish vehicles from other objects. The tracking software may beconfigured in such a way to specifically monitor whether a vehiclehaving any size or style is positioned in the predetermined location(e.g., in a service bay of an oil change shop).

The router 38 is connected to the PoE switch and is also connected tothe DVR/NVR 32, or other device for recording video. The router 38 isalso connected to the processing device 26 and memory device 28 of apersonal computer, laptop computer, tablet, etc.

The DVR/NVR 32 may also be connected to a microphone or other type ofinput device 36 for receiving audio, video, or other signals. Inembodiments regarding a vehicle service business, the microphone may bemounted in a service bay where the vehicle is serviced. For example, themicrophone may be mounted on a bay podium CSR screen on a bottom screenwith Chromebit on top.

The router 38 may be connected in the system 10 to a broadband gateway,which may in turn be a gateway for connection to the Internet 20. Thesystem 10 further includes a point-of-sale (POS) router and a POS deviceof the POS system 16 connected to the broadband gateway 18. If abusiness has a plurality of store locations, the router 38 of eachlocation may be used to connect the cameras, switches, DVR/NVRs, PCs,and microphone to the Internet 20, where the information can be analyzedby a server.

The system 10 may be used as surveillance equipment to capture, measure,and analyze data. The surveillance equipment may be used in manydifferent types of environments, such as in a quick service restaurant(QSR), a quick lube industry, asphalt/material plants, parking garages,etc. In particular, the cameras 12 in the system 10 may be used tomonitor predetermined locations where vehicles, people, or other objectsmay remain for a certain amount of time.

Software for analyzing the camera views can be stored on anon-transitory computer readable medium (e.g., in the memory device 28)and may include logic that can be executed by the processing device 26.For example, the software may be used to turn the surveillance systeminto an intelligent network of real-time sensors. According to someembodiments, the software may include the object/space tracking module42 stored in the memory device 28 and executed by the processing device26. In other embodiments, the object/space tracking module 42 may beconfigured, at least partially, as hardware that is incorporated in theprocessing device 26 or other parts of the computer system 14.

The object/space tracking module 42 may be capable of determining when apredetermine type of object (e.g., vehicle, person, etc.) is located ata predetermined location or zone (e.g., in a service bay, in a queue,etc.). Also, the object/space tracking module 42 can help tracklogistics of customer vehicle traffic and day-to-day operations and canprovide accurate data that is visually verifiable. The object/spacetracking module 42 may be able to provide many of the functions ofidentifying when an object is positioned in the predetermined zones andcan measure the amount of time that the object remains in that zone. Theobject/space tracking module 42 may include sufficient flexibility to beused in various environments where a determination can be made as towhether certain types of objects to be sensed are present or when theyfirst appear in the predetermined zones and when the objects leave thatzone.

The object/space tracking module 42 can be easily deployed, scaled, andupdated as needed. In some embodiments, the object/space tracking module42 may be configured as upgradeable firmware in the computer system 14.

In one embodiment, the object/space tracking module 42 may be configuredto utilize a first camera 12-1 to determine when a recognizable vehicleenters a zone defined within the view of the camera. The recognizablevehicle may be defined as any object that occupies at least a certainamount or percentage of space within a certain zone in the camera'sview. The camera 12 and zones can be set up ahead of time and configuredin the system 10 to allow the object/space tracking module 42 toproperly distinguish a vehicle from other objects.

A first camera 12-1, such as a fish-eye camera or other 360 degreecamera, may be configured to capture multiple lanes. For example, thefish-eye camera can monitor multiple queue lanes of an oil change shopthat lead to multiple bays. From the fish-eye view, the object/spacetracking module 42 may be configured to designate multiple areas withinthe camera views that are indicative of waiting zones. Thus, the imagedata from this one camera may be utilized to determine multiple events(e.g., arriving, leaving) of multiple vehicles in multiple queue lanes.In some embodiments, the image data may also be used to determinemultiple positions in the queue lanes.

The first camera 12-1 may detect when the vehicle first occupies atleast a minimum amount of space of the detection zone and then records afirst time (t1) to indicate when the vehicle first arrives.Alternatively, the system 10 may determine when the vehicle occupies theminimum amount of space, but then may wait until the vehicle comes to acomplete stop. A stop condition may be determined when the view of thevehicle no longer changes. Then, the same camera 12-1 may be used todetect when that vehicle leaves that zone such that the vehicle nolonger occupies that minimum amount of space within that detection zoneand a second time (t2) is determined to indicate when the vehicle leavesthat spot. From the first and second times (t1 and t2), a first lengthof time or dwell time (t2-t1) can be determined representing how longthe vehicle occupied the zone.

In some cases, the first dwell time may represent a first zone, such asa queue where a customer's vehicle waits to receive service. In the oilchange business scenario, the queue may be located outside the bay.Then, when the vehicle leaves this first area, the vehicle may pull intoanother zone, such as into the bay itself or other area where service isperformed. In a fast food drive-through lane, one zone may be an areanext to a menu screen where the customer places an order, a second zonemay be an area outside a payment window where the customer pays for theorder, and a third zone may be outside of a pick-up window where thecustomer picks up his or her food.

While the vehicle is in the first zone, the object/space tracking module42 may be configured to identify the vehicle using recognitionalgorithms. In the second zone, a second camera 12-2 may be used tocapture an image of the vehicle at substantially the same angle anddistance from the vehicle so that the image views captured by the twocameras will be substantially the same. In this way, the object/spacetracking module 42 may be configured to more easily match up therecognition data to verify that the vehicle captured by the secondcamera 12-2 is the same vehicle captured by the first camera 12-1.

When the same vehicle arrives within view of the second camera 12-2 andoccupies at least the minimum amount of space of the detection zone, athird time (t3) is detected. The object/space tracking module 42 can usean object recognition algorithm to determine if the same vehicle is inthe second detection zone. With respect to a drive-through window of aQSR, vehicle recognition may be needed if vehicles from multipleordering/menu lanes merge into a single payment window lane. Also,vehicle recognition may also be needed if one or more vehicles may bepositioned in between the various recognition zones. For example, afront vehicle may be positioned at a pick-up window, a back vehicle maybe positioned at a payment window, and one or more vehicles may bepositioned between the front and back vehicles. Since these intermediatepositions may be outside of any camera detection zones, the object/spacetracking module 42 is configured to keep track of the various vehiclesto determine the appropriate times for each customer.

Returning to the example of the vehicle having remained in the firstzone for a length of time from time t1 to time t2, and then havingarrived at the second zone at t3, a fourth time (t4) is detected whenthe vehicle leaves the second zone. Therefore, an amount of time thatthe vehicle stays in the second zone (e.g., second dwell time) can bedetermined by subtracting the third time from the fourth time (t4-t3).To summarize, the second time t2 minus the first time t1 equals theamount of time that the vehicle remains in the first zone; and thefourth time t4 minus the third time t3 is the amount of time that thevehicle remains in the second zone.

The object/space tracking module 42 can also analyze the images from thefirst camera 12-1 and second camera 12-2 to match up the times t1, t2,t3, and t4 with the appropriate vehicle. The times and running times foreach vehicle are monitored continuously. As mentioned above, the cameras12 may be arranged during a set-up stage so that the view of the vehicleis substantially the same. In this way, the object/space tracking module42 can properly analyze the tracking of each vehicle by similar imagecharacteristics obtained by each camera 12.

Another way to track a specific vehicle is by analyzing a differencebetween the second time t2 (i.e., when the vehicle leaves the firstzone) and the third time t3 (i.e., when the vehicle arrives at thesecond zone). For example, in the oil change shop, the vehicle will movefrom the zone within the queue to a designated position in the bay. Theobject/space tracking module 42 can determine if the difference in thesecond and third times (t3-t2) is a reasonable difference. For example,it may be determined that a vehicle will normally take between fiveseconds and 20 seconds to move from the queue position to the bayposition. If the transition time is within normal time limits, then thesystem 10 determines that this is the same vehicle moving from the zoneof the first camera 12-1 to the zone of the second camera 12-2.

Otherwise, an inaccuracy can arise if a customer pulls up to the queueposition long enough to be recognized, but then leaves without pullingin the bay. In this scenario, times t1 and t2 may be determined. Then,in this example, if another vehicle pulls into the bay after a maximumtransition time (e.g., more than 20 seconds later) with respect to timest2 and t3, the system 10 may determine that this is a different vehicle.

In some situations, a vehicle may not be positioned in the queue longenough to be detected as waiting for service. For example, if t2-t1 isbelow a certain amount of time (e.g., less than 15 seconds), then thesystem 10 may determine that the vehicle has not waited for service, butpossibly the customer has simply stopped to ask questions.

Considering again the transition time between zones (i.e., from t2 tot3), the transition time from one zone to another may be determined tobe legitimate if the time is above a minimum time and below a maximumtime. In a QSR environment, a “normal” transition time may be within twoto six seconds, or any other reasonable time frame based on variousfactors. The minimum and maximum times can be established during a setup stage when the system 10 is first installed. The various factors thatmay be considered during installation may include the length of lanes,sharp curves in the lanes, or other factors that may affect thetransition times. Therefore, the system 10 can be customized for eachindividual store or shop during installation.

During use, the object/space tracking module 42 may be configured tomonitor whether a vehicle moves from one zone to another in a reasonableamount of time. This can be used to keep track of different vehicles andto determine other issues, such as a stalled vehicle, a minor autoaccident, etc.

Also, the object/space tracking module 42 may be configured to determinea first difference (ΔT1) between the second time t2 mentioned above andthe first time t1 and/or a difference (ΔT2) between the fourth time t4and the third time t3. These time periods (ΔT1 and ΔT2) represent dwelltimes, or the amounts of time that the vehicle remains in each zone. Inan oil change shop, the first time amount (ΔT1) that the vehicle dwellsin the first zone (e.g., the queue) may not necessarily represent acustomer wait time. For example, if a customer pulls up in the queue, heor she may be greeted by a representative who may obtain customerinformation and receive instructions regarding what kinds of servicesthe customer wishes to receive. This time would therefore not be countedas a wait time since the customer is actually being serviced. Also, acustomer may wish to get information (e.g., cost of services, wait time,etc.) and may then drive away without receiving any services. In someembodiments, the calculated wait time may be reduced if it is determinedthat the customer was already receiving service (e.g., receiving answersto questions, providing customer information, or involved in otherdiscussions with the service professional). All or a portion of thistime can be discarded, based on how the system is initially set up. Insome service industries, certain times can be added or subtracted basedon various factors that may be unique to the business, such as drivinglanes, store layout, business procedures, etc.

The values ΔT1 and ΔT2 can be analyzed by the system 10. A minimum waittime and/or service time may be set to determine if the customeractually remained in the locations long enough to receive a service. Forexample, in the QSR store, a vehicle may simply be driving around thebuilding. If the vehicle is identified as occupying enough of the zone,but then leaves the zone within a second or so, the object/spacetracking module 42 may be configured to identify that this vehicle isnot waiting for service, but is simply passing through. If a timerstarts to indicate an arrival event, but then the vehicle leaves thezone before the minimum time period is reached (i.e., if t2-t1 is toosmall), the timer information may be discarded. Otherwise, after theminimum time period is reached, the timer information is kept.

According to another implementation, the system 10 includes informationfrom the POS system 16 to monitor wait times. In conventional systems,service time at a vehicle repair or oil change shop may start when avehicle identification number (VIN) is first entered into a POS device.The service end time may be recognized at the time the customer pays forthe service using the POS device. However, the total wait time may beinaccurate because it relies on the entry of the VIN number to start thetimer. On the other hand, the timers of the present disclosure useinformation obtained from cameras 12 to determine a real time when acustomer actually arrives at the shop. Thus, the system 10 of thepresent disclosure can provide much more accurate wait time information.

Also, the POS system 16 may be used to match the services that thecustomer receives with the customer wait times. Therefore, the system 10can determine if the wait time is appropriate with respect to theservices received. For example, if a customer only receives an oilchange, then a predetermined amount of time should be expected tocomplete the service. However, if a customer receives multiple services(e.g., an oil change, transmission service, differential service, etc.),the longer wait time would be expected. Therefore, based on informationobtained from the POS system 16 regarding services received and paidfor, the system 10 can determine if the wait time for those services isnormal.

A “snapshot” of the vehicle may be recorded after the vehicle hasremained in a service zone for a predetermined time period. The snapshotcan be matched with payment information of the POS system 16. In someembodiments, the snapshot can be displayed for the customer to see toverify that they are paying for the correct vehicle and service. Thesnapshot information can also be used in a QSR drive-through to enable acashier at a payment window to match up the correct order with thecorrect vehicle. The same snapshot information can also be provided tothe person at the food presenting window to make sure that the customeris picking up the correct order.

The system 10 may include storing video footage from the cameras 12 inthe DVR/NVR 32. Then, if a simple service took much longer thanexpected, the system 10 may be configured to allow a manager to look atthe footage to find out why the service took so long. The video footagecan also be used for other purposes as well, as will be understood byone of ordinary skill in the art.

FIG. 3 shows an example of a display view 50 of a customer displaydevice 34 according to one embodiment. The display view 50 may beconfigured to show aspects of a service that is being performed for acustomer. For instance, in the example shown in FIG. 3, the customer,perhaps waiting in a waiting area of an oil change shop, may be able toview the display view 50 on a monitor or television screen to see theprogress being made to the customer's vehicle.

The display view 50 may include a service time display 52, which may beconfigured to show a running time of how long the service has beentaking. In this example, the service time display may show a messagesuch as “Your service time is:” along with the running time (e.g.,“10:25” in this example). Therefore, the customer will know how long theservice is taking. In some embodiments, the displayed service time 52may include just the time of the actual servicing of the vehicle, whilein other embodiments, the displayed service time 52 may also include thewait time in the queue before the vehicle was driven into the bay.

Also illustrated in the display view 50 is a first camera view 54 and asecond camera view 56. It should be known that any number of cameraviews (e.g., zero, one, or multiple camera views) can be included in thedisplay view 50. In the embodiment illustrated in FIG. 3, it should beunderstood that multiple cameras 12 (i.e., two in this example) are usedto show different views of the one zone where the vehicle receivesservice.

From the display view 50, a customer can see when his or her vehicle hasentered the bay and when the service time display 52 resets to 0:00 tobegin running the service time. The customer can also see, from thefirst and second camera views 54, 56 the progress being made on thevehicle.

One camera 12 (i.e., the camera that captures the view 54) may be usedfor two purposes. A first purpose is to provide the view shown in thefirst camera view 54 that is displayed in a display device 34, which maybe viewable by a customer or an employee of the shop. A second purposeis to sense when a vehicle enters or leaves the bay or otherpredetermined zone, as mentioned above.

The other view (i.e., the second camera view 56) may show a view from asecond camera 12. In this example, the second camera 12 may show asecond view from a below-ground position. This view shows a mechanic orother service professional performing some type of service on thevehicle. For example, in the illustrated example, the second camera view56 shows the service of removing old motor oil from the vehicle. Thethree views, that is, the service time display 52, the bay view (orfirst camera view 54), and the below-ground view (or second camera view56) may be displayed on a single customer display device 34 or onmultiple display devices 34 provided for the customer. For example, theone or more displays may be located in a waiting area.

FIG. 4 shows another example of an embodiment of a display device 34,36. In this embodiment, the display device 34, 36 shows a display view60 on a computer screen of the computer system 14. The display view 60can be configured to show aspects of in-progress services at a shop.

According to FIG. 4, the display view 60 shows a screen shot orgraphical user interface (GUI) that may be displayed on a screen of thecomputer system 14 that is used by a service professional. In thisexample, the computer system 14 may be available only to the people whowork at an oil change shop. The display view 60 allows the user to viewthree different pages, which can be accessed using selectable tabs 62,64, 66 at the top of the window of the display view 60. FIG. 4 shows thedisplay view 60 representing when a “live” tab 62 has been selected,allowing the user to see the current status of the shop. One or morecamera views from cameras 12 may be displayed in the “live” screen.

The GUI or display view 60 of the “live” feed may also include a “targettime” display 68, a “vehicles serviced” display 70, an “average servicetime” display 72, a “next customer wait time” display 74, a “vehicleswho waited” display 76, and an “average wait time” display 78. As shownin the example, the display view 60 shows that the target time display68 shows a target of “15:00” or 15 minutes, which may be a goal for theservice technicians. In other words, based on management goals for thestore or for a number of stores in a region, the service technician cansee the time that is allotted for performing the oil change is 15minutes.

In the example, the display view 60 also shows that “21” vehicles havebeen serviced over a predetermined time period (e.g., the present day).At the end of servicing when a vehicle leaves the bay at the fourth timet4, the system 10 not only records the time period ΔT2, but also countsthat vehicle in the number of vehicles that have been serviced.

The average service time in this example is 20:02. This average time canbe computed from the total time that it took for all the vehicles toreceive service divided by the number vehicles serviced.

Data regarding the next customer wait time (e.g., 04:29), the number ofvehicles that have waited for service (e.g., 10), and the average waittime (e.g., 08:37) can be monitored by the system. These values are alsodisplayed on the display view 60.

The GUI or display view 60 may also include one or more views 80, 82 ofthe bay or bays and/or views of below-ground cameras, etc. For example,view 80 shows a Bay-1 top side view of a vehicle being serviced. Therunning time is shown as “10:34” in this example. Also, another view inthe top left-hand corner of the view 80 shows a predetermined spacewhere another camera 12 is used to view a queue behind Bay-1. In thisexample, a vehicle has been waiting in the queue for 1:59.

Also, view 82 is a Bay-2 top side view and has a running time of “7:04”in this example. Another “in-screen” view in the top left-hand corner ofview 82 shows a queue behind Bay 2 where a vehicle is waiting to receiveservice in Bay 2, which is indicated as “open” to show that no vehicleis in the queue for Bay 2.

FIG. 5 shows an example of another embodiment of a display view 90 thatis displayed when the user of the computer system 14 selects the “data”tab 64. The display view 90 allows the user to see details of thedifferent customers that have had vehicles serviced. The display view 90may show the bay 92 that was being used and the start time 94 or t3 thatthe object/space tracking module 42 detected when a vehicle firstarrived in the bay. In some embodiments, an end time column, not shown,may be included to show when (i.e., t4) the object/space tracking module42 senses that the vehicle had left the bay. The display view 90 GUI mayalso include a service time 96 that is calculated based on the starttime 94 and end time or based on a running time from the start time 94.

If the shop includes a vehicle queue camera that captures when a vehiclefirst arrives at a location where a customer intends to receive aservice, then this camera and the associated software functionality maybe used to determine if the customer had to wait for service, which isdisplayed as a “wait time” 98 (i.e., ΔT1). If not, the wait time will be00:00. However, if it is determined that the customer had to wait, thecamera for detecting the wait time can detect how long the customerwaits before service. The service time 96 and wait time 98 can be addedtogether to calculate the total customer time 100, shown in the nextcolumn of the GUI of the display view 90, which can be calculated as ΔT1plus ΔT2. The last column 102 may include a stored snapshot of a view ofthe particular vehicle being serviced with respect to the other servicedata.

FIG. 6 shows another display view 110, displayed on display device 34 orI/O device 36 of the computer system 14. In the example of FIG. 6, thedisplay view 110 is configured for showing aspects of services atmultiple locations of a store. For example, when a service includesmultiple stages, then the multiple locations or zones representing thevarious stages are monitored. In a quick service restaurant (QSR), thevarious stages may include a first stage of waiting in a queue beforeplacing an order, a second stage of placing the order, a third stage ofwaiting to pay for the order, a fourth stage of paying for the order, afifth stage of waiting to pick-up the order, and a sixth stage ofpicking up the order. In some embodiments, some of these six stages maybe combined for simplicity.

The QSR as shown in the example of FIG. 6 may include a number ofpredetermined locations where a customer vehicle may remain for ameasurable amount of time. For example, a first location may be an“order” location where a customer orders food. The next location may bein front of a window where the customer pays a cashier for the food, asshown in the camera view 120. The third location may be in front of awindow where the customer picks up their food, as shown in the cameraview 122. In some embodiments, there may be Order, Pay, and Pick-Uplocations shown in the various camera views.

The display view 110 may be displayed only for viewing by someoneworking at the QSR (e.g., a restaurant manager) using a personalcomputer. The display view 110 in this example shows two of the multiplelocations mentioned above, but fewer or more views may be displayed inthe display view 110.

In addition to the camera views, the object/space tracking module 42 maybe configured to calculate times and averages based on an analysis ofthe camera views. For example, the display view 110 may include a goal114 a (e.g., 30 seconds), an average 116 a (e.g., 23 seconds), and acurrent running time 118 a (e.g., 01:30) for a current customer. Thegoal, average, and current times may also be shown with respect to afirst location (e.g., Pay). Another location (e.g., Pick-up) may alsohave another goal 114 b (e.g., 30 seconds), an average 116 b (e.g., 12seconds), and a current running time 118 b for a current customer.

In addition, the display view 110 may include a “vehicles served”display 124 (e.g., total number of the vehicles served during the day)(e.g., 135), a “Cash to Pick-up Goal” 126, which refers to the goal forthe time that it takes for a customer to stop in the pay zone (“Cash”)and the pick-up zone (“Pick-up”) drive through lane positions. The timeis calculated by the object/space tracking module 42 from the moment acustomer arrives at the window to pay for his or her food to the momentwhen the customer has received his or her food at the next window anddrives away. In this example, the cash to pick-up time is 00:55 (or 55seconds). Also, the cash to pick-up average display 128 is shown and a“total served today” display 130 of the total number of customers servedthat day (e.g., 1291).

The Cash to Pick-Up (Cash>Pick-Up) may refer to stops in the drive thrulanes. The system may actually time all three stops in a drive thrulane: Order, Pay, and Pick-up. The user (e.g., store manager) mayinitially set up target times and the system 10 is able to measure timesagainst those targets. The GUI may include various colors to representdifferent actual times with target times. The colors may representwhether they are under target time (green), nearing target time(yellow), or over their target time (red). The Cash to Pick-up average128 is simply a running average time at each stop of the drive thru, fora particular location.

In addition, the display view 110 may also include breakfast statistics132, lunch statistics 134, afternoon statistics 136, dinner statistics138, late-night statistics 140, and overnight statistics 142. Each ofthese categories may be used to determine the number customers and thevarious averages during each of those times during the day.

FIG. 7 shows a vehicle lane 143 where multiple services are performed.The vehicle lane 143 includes a first predetermined zone 144, a secondpredetermined zone 145, and a third predetermined zone 146. In otherembodiments, the vehicle lane 143 may include fewer or morepredetermined zones. As an example, the first predetermined zone 144 maybe an ordering zone, the second predetermined zone 145 may be a paymentzone, and the third predetermined zone 146 may be a food pick-up zone.

In addition, during an installation phase, cameras may be installed tomonitor each of the zones 144, 145, 146. For example, a first camera148-1 is configured to monitor the first predetermined zone 144, asecond camera 148-2 is configured to monitor the second predeterminedzone 145, and a third camera 148-3 is configured to monitor the thirdpredetermined zone 146. Preferably, the cameras 148 are positioned atthe same height and angle with respect to the vehicle lane 143 in orderthat the object/space tracking module 42 is able to recognize the samevehicle at different times in the sequence of services, regardless ofwhether one or more vehicles are positioned before and or after thevehicle. The object/space tracking module 42 may be configured todetermine dwell times for each vehicle at each zone 144, 145, 146 andcalculate totals and averages as needed.

FIG. 8 shows an embodiment of a screen display view 150 that may beshown on a customer mobile device for indicating estimated wait times ateach of multiple shop locations. As mentioned above, the location waittime server 22 shown in FIG. 1 can be configured to receive wait timesfrom multiple locations. For example, if an oil change company ownsmultiple stores within a region, the wait times from each location canbe communicated to the location wait time server 22, which in turn canupload this information to a website that displays up to the minuteinformation about the wait times at those shops. From this information,a customer can determine where they can go to get the fastest service ordetermine if the shop nearest to them is busy.

In some embodiments, a wait time application may be available tocustomers. An example of the screen shot (e.g., display view 150) of thewait time application is shown in FIG. 8. The display view 150 includesa map 152 of a region, such as a region centered around the currentlocation of the user. Thus, the application may use GPS to determine thelocation of the user or the user may enter a center location aroundwhich the map 152 can be created.

In this embodiment, a number of icons representing store locations 154may be displayed on the map 152. Information from each store can bemanaged by a central computer or server (i.e., the location wait timeserver 22 shown in FIG. 1) via the Internet 20 and combined to form theillustrated screen shot 150. The location wait time server 22 may beconfigured to estimate the wait time that a customer may experience ifhe or she were to visit the stores at that particular time. The waittime application may be accessible via a personal computer, mobiledevice (e.g., smart phone), or other device able to access a web siteassociated with the service company. The user may also be able to clickon a “map route” associated with each shop marker or store location 154that would assist the user with directions to the particular shops.

FIG. 9 is a flow diagram showing an embodiment of a method 160 fordetermining a time that an object remains at a location. The methodcomprises a first block 162 representing a step of obtaining an image ofa predetermined space. The predetermined space may be a location where avehicle or human receives service or a line or queue in which thevehicle or human waits to begin receiving a service. From the image ofthe predetermined space, the method 160 includes a decision diamond 164,indicating a step of determining if a recognizable object occupies atleast a predetermined amount of the predetermined space. This can bedetected by changes in the images from an empty space to a space beingoccupied by a predetermined type of object. For example, if the objecthaving a certain volume in the camera view is present, then the objectmay be recognized. If a recognizable object is not detected, the methodloops back to decision diamond 164 until an object is detected.

When it is determined in decision diamond 164 that a recognizable objecthas been detected in the space, the method includes a block 166 ofstarting a timer when the recognizable object first enters thepredetermined space. In some embodiments, the method 160 may alsoinclude a block 168 for displaying the image to either a customer or toa shop manager. The image may be a video or single snapshot. The displaymay also include a running time indicating how long the object has beenreceiving service. The method 160 further includes decision diamond 170,which determines if the recognizable object still occupies at least thepredetermined amount of the space. This can be done using the samecamera used to determine when the object originally enters the space,associated with decision diamond 164. If the object still occupies thespace, the method 160 loops back to block 168 where updated video orsnapshots of the object can be displayed.

However, if it is determined in decision diamond 170 that the object nolonger occupies the space, then the method 160 proceeds to block 172,which indicates that the timer is stopped to designate the time when therecognizable object leaves the predetermined space. The method 160 alsoincludes block 174, which determines an amount of time that therecognizable object remains in the predetermined space, which iscalculated by the difference between the start time and the end time todetermine the elapsed time.

Additional methods may include a step of determining the start times andend times for a plurality of recognizable objects that enter and leavethe predetermined space. The methods may further include the step ofcounting the number of recognizable objects that enter and leave thepredetermined space over a predetermined period of time, such as withinan hour or a day. The methods may further comprise the step ofdetermining an average elapsed time based on the number of recognizableobjects that enter and leave the predetermined space and the determinedamounts of time that each recognizable object remains in thepredetermined space.

The methods may further include a first step of determining an averageelapsed time of a number of objects for each of a plurality ofpredetermined spaces located at a plurality of service facilities. Then,the methods may also include determining an estimated wait time at eachservice facility. The methods may then upload the estimated wait timesto enable a user to access the estimated wait times using a mobileapplication.

In some embodiments, the methods may further include steps ofdetermining a running time indicative of an amount of time that therecognizable object has been in the predetermined space and displayingthe running time to a customer.

It should be known that the system 10 may be able to distinguishrecognizable objects from those that do not meet certain image criteria.For example, the object/space tracking module 42 may be configured todetermine when a vehicle is in the bay, as opposed to maybe a tool boxor a person standing in the bay. The system 10 may utilize clearlydefined “lanes” that are drawn when the system 10 is first set up ateach location and when cameras 12 are installed. Once the vehicle entersinto the clearly defined zones drawn in the bay, the system 10 can beginto time the services.

FIG. 10 (i.e., FIGS. 10A and 10B) is a method 180 for tracking servicewait times for a vehicle. FIG. 10 may be performed after cameras 12 anda computer system 14 are installed in a service shop or in a servicelane.

The method 180 includes the step of obtaining image data from a firstcamera, as indicated in block 182. The method 180 also includesutilizing the image data from the first camera to determine if anyvehicle is present in a first predetermined zone. In some embodiments,the method 180 may include utilizing the image data to determine if afirst condition is met, whereby the first condition is met when anyvehicle occupies at least an amount of space in the first predeterminedzone that is greater than a first predetermined threshold. The firstpredetermined threshold may be a minimum volume in the camera view thatmust change for the method to detect that a vehicle is present, asopposed to a smaller object.

In decision diamond 186, the method 180 indicates that a determinationis made as to whether a vehicle is present. If no vehicle is present,the method 180 loops back to block 182 to obtain additional image data.If it is determined in decision diamond 186 that a vehicle is present,the method proceeds to block 188. As indicated in block 188, the method180 includes the step of recognizing image characteristics of a firstvehicle in the first predetermined zone.

As indicated in block 190, the method 180 determines a first start timewhen the first vehicle is initially present in the first predeterminedzone. In other words, the first start time is indicative of when theabove-mentioned first condition is first met by the first vehicle. Block192 indicates a step of determining a first end time when the firstvehicle leaves the first predetermined zone. This determination can bemade by detecting the first end time, which occurs after the first starttime, when the first condition is no longer met by the first vehicle.

The method 180 further includes the step of calculating a first dwelltime, as indicated in block 194, representing the time that the firstvehicle remains in the first predetermined zone. The first dwell timecan be calculated from the first start time and the first end time.

In some embodiments, the method 180 may also include decision diamonds196 and 200 for comparing the dwell time with minimum and maximumthresholds. As indicated in decision diamond 196, the method 180determines if the first dwell time is greater than a minimum threshold.If it does not exceed the minimum threshold, representing a condition inwhich a vehicle occupies the first predetermined zone for too short of atime to be considered as a customer receiving service, the method 180goes to block 198, which indicates that the time is reset and the method180 returns back to the beginning to start again. However, if the firstdwell time exceeds the minimum threshold, the method 180 proceeds todecision diamond 200.

Decision diamond 200 indicates that the method 180 determines if thefirst dwell time is less than a maximum threshold. If not, indicatingthat service has taken too long (e.g., based on preset goals), then themethod goes to block 202, which indicates that an indication is providedthat an excessive amount of time has been taken to service the vehicle.In some embodiments, the indication may be an audio signal or a visualsignal (e.g., changing a color of an indication to red). However, if thefirst dwell time is found to be below the maximum threshold in decisionblock 200, the method 180 jumps ahead to “A,” which resumes in FIG. 10B.The steps shown in FIG. 10A may represent the actions taken with respectto a single camera, whereas the steps shown in FIG. 10B may representthe actions taken with respect to a second camera.

As shown in FIG. 10B, the method 180 includes the step of obtainingimage data from a second camera according to block 204. The method 180utilizes the image data from the second camera (i.e., block 206) todetermine if any vehicle is present in a second predetermined zone. Insome embodiments, the presence of a vehicle can be determined bydetecting if a second condition is met, whereby the second condition ismet when any vehicle occupies at least an amount of space in the secondpredetermined zone that is greater than a second predeterminedthreshold.

Method 180 further includes determining if a vehicle is present, asdetermined with respect to decision diamond 208 If not, the method 180returns back to block 204 to continue obtain image data from the secondcamera. However, if a vehicle is detected as being present, the method180 proceeds to block 210. As indicated in block 210, a step isperformed to recognize image characteristics of the first vehicle in thesecond predetermined zone. As indicated in decision diamond 212, themethod 180 determines if the recognized image characteristics are sharedwith the first vehicle to detect if it is the same vehicle. If not, thenin some embodiments, the method 180 may proceed to “B,” which leads toblock 198 shown in FIG. 10A to reset the timers and return to thebeginning of the method 180. If, on the other hand, the vehicle is thesame vehicle (i.e., the first vehicle), then the method 180 proceeds toblock 214.

As indicated in block 214, a step of determining a second start time isconducted, the second start time being a time when the first vehicle isinitially present in the second predetermined zone. Determining that thefirst vehicle is present may be performed by determining when the secondcondition (detected in block 206) is first met by the first vehicle. Asindicated in block 216, the method 180 includes determining a second endtime when the first vehicle leaves the second predetermined time. Thisdetermination can be made by detecting, after the second start time,when the second condition is no longer met by the first vehicle.

Method 180 further includes calculating a second dwell time, asindicated by block 218, which may be calculated from the second starttime and the second end time. The method 180 may further includedetermining if the second dwell time is greater than a minimumthreshold. If not, then the method 180 may be reset. If so, the method180 may proceed to decision diamond 222, which indicates that it isdetermined whether the second dwell time is less than a maximumthreshold. If it is, the method 180 skips block 224. Otherwise, block224 is executed, which includes the step of providing an indication thatan excessive dwell time has been reached or surpassed.

From the first dwell time (i.e., block 194) and the second dwell time(i.e., block 218), a total dwell time can be calculated, as indicated inblock 226. As indicated in block 228, the method 180 includes a step ofdisplaying one or more aspects of the services. For example, thedisplaying step may include displaying an image of the first vehicle,displaying the first dwell time, displaying the second dwell time,and/or displaying the total dwell time. This information can bedisplayed on a display screen that is designated for use by a customeror by a worker at the service facility.

These and other embodiments are considered to be within the spirit andscope of the present disclosure and are not limited to the examplesdiscussed above.

1. A system comprising: a camera configured to capture an image of avehicle in a predetermined space; a processor configured to: utilize theimage from the first camera to determine if any vehicle occupies atleast an amount of space in the predetermined space greater than apredetermined threshold or recognize image characteristics of a firstvehicle in the first predetermined space; determine a start time whenthe vehicle is determined to have entered the predetermined space;determine an end time when the vehicle leaves the predetermined space;and calculate an elapsed time, based on the start time and the end time,when the vehicle remained in the predetermined space.
 2. The system ofclaim 1, wherein the processor is configured to determine the starttimes and end times for a plurality of vehicles that enter and leave thepredetermined space.
 3. The system of claim 2, wherein the processor isfurther configured to count the number of vehicles that enter and leavethe predetermined space over a period of time.
 4. A system comprising: acamera configured to capture an image of a vehicle in a predeterminedspace; a processor configured to determine a start time when the vehicleenters the predetermined space, determine an end time when the vehicleleaves the predetermined space, and calculate an elapsed time, based onthe start time and the end time, when the vehicle remained in thepredetermined space.
 5. The system of claim 4, wherein the processor isconfigured to determine the start times and end times for a plurality ofvehicles that enter and leave the predetermined space.
 6. The system ofclaim 5, wherein the processor is further configured to count the numberof vehicles that enter and leave the predetermined space over a periodof time.
 7. The system of claim 6, wherein the processor is furtherconfigured to determine an average elapsed time based on the number ofvehicles that enter and leave the predetermined space and the elapsedtime that each vehicle remained in the predetermined space.
 8. Thesystem of claim 7, further comprising a plurality of predeterminedspaces of a service facility and a plurality of cameras each configuredto capture an image of a vehicle in a respective predetermined space,wherein the processor is configured to determine an average elapsed timefor each of the predetermined spaces.
 9. The system of claim 8, whereinthe plurality of predetermined spaces are located at a plurality ofservice facilities, and wherein the processor is configured to determinean estimated wait time at each service facility and upload the estimatedwait times to a server configured to enable a user to access theestimated wait times using a mobile application.
 10. The system of claim4, further comprising a plurality of predetermined spaces in a vehiclelane and a plurality of cameras, wherein each camera corresponds to arespective predetermined space; wherein the processor is configured todetermine a start time when the vehicle enters each predetermined space,determine an end time when the vehicle leaves each predetermined space,and calculate dwell times, based on the start times and the end times,when the vehicle remains in each of the predetermined spaces.
 11. Thesystem of claim 10, wherein the processor is configured to recognizeimage characteristics of the vehicle in each predetermined space todistinguish one vehicle from another.
 12. The system of claim 4, whereinthe processing device is configured to determine a running timeindicative of an amount of time that the recognizable object has been inthe predetermined space.
 13. The system of claim 12, further comprisinga display device configured to display the running time to a customer.14. A method comprising: determining a start time when a vehicle entersa predetermined space based on processing an image capturing thepredetermined space; determining an end time when the vehicle leaves thepredetermined space; and determining a dwell time that the vehicleremains in the predetermined space, the dwell time determined from thestart time and the end time.
 15. The method of claim 14, furthercomprising the step of determining the start times and end times for aplurality of vehicles that enter and leave the predetermined space. 16.The method of claim 15, further comprising the step of counting thenumber of vehicles that enter and leave the predetermined space over aperiod of an hour, a portion of a day, a day, a week, a month, or ayear.
 17. The method of claim 16, further comprising the step ofdetermining an average elapsed time based on the number of vehicles thatenter and leave the predetermined space and the determined amount oftime that each vehicle remains in the predetermined space.
 18. Themethod of claim 17, further comprising the steps of: determining anaverage elapsed time of each of a plurality of predetermined spaceslocated at a plurality of service facilities; determining an estimatedwait time at each service facility; and uploading the estimate waittimes to enable a user to access the estimated wait times using a mobileapplication.
 19. The method of claim 14, further comprising the step ofdetermining a running time indicative of an amount of time that thevehicle has been in the predetermined space.
 20. The method of claim 19,further comprising the step of displaying the running time to acustomer.